Consumer Interaction Experience API

1.0.x
(0 reviews)

Error responses for Gigya

The different responses for Gigya

Http statusCode:

  • 202 - The successful scenario the response looks like this

{
"statusCode": "202",
"details": "Data submission was successful",
"statusMessage": "Accepted"
}

  • 400:

    a) When the payload doesn't match with the gigya schema

{
"statusCode": "400",
"details": "Gigya schema validation errors",
"statusMessage": "subscriptions.optInOptOut.SVC_GB_BH01162_EML_Newsletter.email.isSubscribed"
}

b) For invalid Brand or market in input payload

{
"statusCode": "400",
"details": "com.unileverservices.pdc.integration.APIKeyLookupFailure: No API Key was found for the market/brand passed.",
"statusMessage": "Bad Request"
}

  • 404: For invalid path

{
"statusCode": "404",
"statusMessage": "Resource not found",
"details": "/consumer_interaction_creae"
}

  • 415: For unsupported input type
{
"statusCode": "415",
"statusMessage": "Unsupported media type",
"details": "Unsupported mediaType"
 }
  • 405: For incorrect method

{
"statusCode": "405",
"statusMessage": "Method not allowed",
"details": "HTTP Method put not allowed for : /consumer_interaction_create"
}

  • 500:

{
"statusCode": "500",
"statusMessage": "Internal Server Error",
"details": "A server-side exception occurred that prevented the system from correctly returning the result."
}

Reviews